Search code, repositories, users, issues, pull requests...

Patch Changes

#439 c1d64c3 Thanks @JounQin! - chore: bump unrs-resolver to v1.6.2

Full Changelog: import-js/eslint-import-resolver-typescript@v3.10.0...v3.10.1

`v3.10.0`

Minor Changes

#413 89c2795 Thanks @JounQin! - chore: housekeeping, bump all (dev) deps

Migrate rspack-resolver to rebranding unrs-resolver for more targets support and other bug fixes

Full Changelog: import-js/eslint-import-resolver-typescript@v3.9.1...v3.10.0

`v3.9.1`

Patch Changes

#382 4a9176e Thanks @JounQin! - fix: use rspack-resolver fork for pnp support

`v3.9.0`

Minor Changes

#379 6814443 Thanks @JounQin! - feat: migrate enhanced-resolve to oxc-resolver

`v3.8.7`

Patch Changes

#377 a14fdd9 Thanks @carlocorradini! - fix: include mapper with no files and force non-dynamic projects to use absolute paths

`v3.8.6`

Patch Changes

#374 c9d5ab0 Thanks @JounQin! - fix: add support for importing with .js extension as tsx importee

`v3.8.5`

Patch Changes

#372 366eeaf Thanks @carlocorradini! - fix: if file has no corresponding mapper function, apply all of them, starting with the nearest one.

`v3.8.4`

Patch Changes

#370 c940785 Thanks @JounQin! - fix: support multiple matching ts paths

`v3.8.3`

Patch Changes

#360 8192976 Thanks @carlocorradini! - Force tiniglobby to expand dot directories
#360 8192976 Thanks @carlocorradini! - Update tinyglobby to latest version

`v3.8.2`

Patch Changes

#357 5fd349e Thanks @carlocorradini! - Update the tinyglobby to the latest version to solve performance regressions.

`v3.8.1`

Patch Changes

#352 0c6303d Thanks @carlocorradini! - Set cwd while resolving tsconfig include

`v3.8.0`

Minor Changes

#345 fcc8883 Thanks @carlocorradini! - Enable the mapper function just for a set of allowed files. Improves project discovery using glob and POSIX separator.
#346 c124e87 Thanks @carlocorradini! - Update get-tsconfig to the the latest version. We now support the ${configDir} variable, introduced in TypeScript 5.5.

`v3.7.0`

Minor Changes

#326 93ea130 Thanks @SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

Previously

// eslint.config.js
module.exports = {
  settings: {
    'import-x/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
      // or
      require.resolve('eslint-import-resolver-typescript'):
        alwaysTryTypes: true,
      }
    }
  }
}

Now

// eslint.config.js
const {
  createTypeScriptImportResolver,
} = require('eslint-import-resolver-typescript')

module.exports = {
  settings: {
    'import-x/resolver-next': [
      createTypeScriptImportResolver({
        alwaysTryTypes: true,
      }),
    ],
  },
}

Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

`v3.6.3`

Patch Changes

#305 f8d7b82 Thanks @SukkaW! - Fix resolve for node:test, node:sea, and node:sqlite without sacrificing installation size
#288 a4c6c78 Thanks @SunsetTechuila! - fix: ignore bun built-in modules

lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)

`v12.1.1`

This release adds a short meta.docs.description to each rule. Thanks to fisker Cheung (@fisker)!

`v12.1.0`

This release adds TypeScript type definitions for the plugin itself. This is useful when you use TypeScript to check your ESLint configuration. It assumes that you install @types/eslint yourself. Thanks to @Logicer16!

sindresorhus/eslint-plugin-unicorn (eslint-plugin-unicorn)

`v56.0.1`

expiring-todo-comments: Fix compatibility with ESLint 9.15 (#2497) 16b09d3

veritem/eslint-plugin-vitest (eslint-plugin-vitest)

`v0.5.4`

Features

support old Eslint configuration
update dependencies

`v0.5.3`

Bug Fixes

configs in plugin declaration file (#428) (a554dd2)

`v0.5.2`

Features

no-focused-tests: add autofix (#424) (07be616)

`v0.5.1`

Bug Fixes

no-focused-tests: support .each template strings (#420) (36e5b9a)

`v0.5.0`

‼️ Breaking Change 🚨

This version only supports new eslint flat config!

If you run into issues, consider downgrading and opening an issue. Remember to include a minimum repro example to help me fix issues quickly!

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.5.0...v0.5.0

prettier/prettier (prettier)

`v3.6.2`

Markdown: Add missing blank line around code block (#17675 by @fisker)

<!-- Input -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

<!-- Prettier 3.6.1 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```
   1. Another
   2. List

<!-- Prettier 3.6.2 -->
1. Some text, and code block below, with newline after code block

   ```yaml
   ---
   foo: bar
   ```

   1. Another
   2. List

`v3.6.1`

TypeScript: Allow const without initializer (#17650, #17654 by @fisker)

// Input
export const version: string;

// Prettier 3.6.0 (--parser=babel-ts)
SyntaxError: Unexpected token (1:21)
> 1 | export const version: string;
    |                     ^

// Prettier 3.6.0 (--parser=oxc-ts)
SyntaxError: Missing initializer in const declaration (1:14)
> 1 | export const version: string;
    |              ^^^^^^^^^^^^^^^

// Prettier 3.6.1
export const version: string;

Miscellaneous: Avoid closing files multiple times (#17665 by @43081j)

When reading a file to infer the interpreter from a shebang, we use the
n-readlines library to read the first line in order to get the shebang.

This library closes files when it reaches EOF, and we later try close the same
files again. We now close files only if n-readlines did not already close
them.

`v3.6.0`

`v3.5.3`

Flow: Fix missing parentheses in `ConditionalTypeAnnotation` (#17196 by @fisker)

// Input
type T<U> = 'a' | ('b' extends U ? 'c' : empty);
type T<U> = 'a' & ('b' extends U ? 'c' : empty);

// Prettier 3.5.2
type T<U> = "a" | "b" extends U ? "c" : empty;
type T<U> = "a" & "b" extends U ? "c" : empty;

// Prettier 3.5.3
type T<U> = "a" | ("b" extends U ? "c" : empty);
type T<U> = "a" & ("b" extends U ? "c" : empty);

`v3.5.2`

Remove `module-sync` condition (#17156 by @fisker)

In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.

`v3.5.1`

Fix CLI crash when cache for old version exists (#17100 by @sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#17101 by @remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

`v3.5.0`

`v3.4.2`

Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#16891 by @fisker)

// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

Fix non-idempotent formatting (#16899 by @seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

`v3.4.1`

Remove unnecessary parentheses around assignment in `v-on` (#16887 by @fisker)

<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

`v3.4.0`

`v3.3.3`

Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(foo`tagged template`)
class X {}

Support `@let` declaration syntax (#16474 by @sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@&#8203;let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

`v3.3.2`

Fix handlebars path expressions starts with `@` (#16358 by @Princeyadav05)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

`v3.3.1`

Preserve empty lines in front matter (#16347 by @fisker)

<!-- Input -->
---
foo:
  - bar1

  - bar2

  - bar3
---
Markdown

<!-- Prettier 3.3.0 -->

---
foo:
  - bar1
  - bar2
  - bar3
---

Markdown

<!-- Prettier 3.3.1 -->
---
foo:
  - bar1

  - bar2

  - bar3
---

Markdown

Preserve explicit language in front matter (#16348 by @fisker)

<!-- Input -->
---yaml
title: Hello
slug: home
---

<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---

<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---

Avoid line breaks in import attributes (#16349 by @fisker)

// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
  "json" };

// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };

`v3.3.0`